Repository navigation
Conversation
Failed release fetches were silently skipped, so a transient API error produced a changelog with most repositories missing, which got published and restored by the next hourly run. Retry failed fetches and abort if they keep failing, so nothing is written or committed.
The publish workflow runs robo changelog as a separate, authenticated step which overwrites the result. The run in build:docs is unauthenticated and only consumes API rate limit.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
processChangelog()silently skipped repositories whose release fetch failed. A temporary GitHub API error produced a changelog with most repositories missing. That version was published, and the next hourly run restored it.Examples (truncated → restored):
Changes
robo changelogexits with an error before writing the file, so the publish step doesn't run and the next hourly run tries again.build:docs: that run was unauthenticated and its output was overwritten by the separaterobo changelogstep anyway. It only used up API rate limit.Note
If the changelog step fails, that hour's other docs updates are published with the next successful run.